Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Two-phase commit

Two-phase commit is not supported when using the OpenEdge DataServer to access non-OpenEdge databases. Without two-phase commit, in some cases you cannot guarantee that either all of the database updates or none of the database updates are written at the end of the transaction. This happens when there are updates to several databases within one transaction, and when one or more of those databases are accessed through a DataServer.

The Progress Dynamics environment always has multiple databases connected. This makes the lack of two-phase commit of special interest when you use DataServers in Progress Dynamics. However, the design of the Progress Dynamics framework limits where a single transaction might update more than one database. The main areas of concern are for the auditing and comment support.

The built-in auditing and commenting features of Progress Dynamics are optional. If you use these features and an OpenEdge DataServer, then a failure during a transaction could cause an inconsistent state in the databases. Although the window for this type of failure is small, you might want to avoid using these optional features if you cannot afford a failure of this type.